Organizational Readiness Evaluations
ORE
The U.S. Army Air Defense Command (ARADCOM) conducted Organizational Readiness Evaluations (OREs) on a periodic but not strictly fixed schedule, and the exact frequency could vary by unit, higher command directives, and the time period within the 1960s.
That said, based on historical accounts from Nike missile personnel and ARADCOM practices:
- Typically, an ORE occurred about once per year per site as a formal, graded evaluation.
- In addition, units often had no-notice or short-notice drills (sometimes called alerts, simulations, or “tactical evaluations”) multiple times per year to maintain readiness.
- Some sites experienced more frequent evaluations (2–3 per year) during periods of heightened Cold War tension or when performance issues had been identified. OREs were designed to simulate real combat conditions—often including:
- Surprise alerts (day or night)
- Full manning of positions
- Missile readiness and launch simulation
- Communications and command response under pressure
1. Surprise Alert The drill almost always began with a no-notice alert, often at inconvenient hours (middle of the night, shift change, bad weather).
- Sirens, klaxons, or direct phone alerts would sound
- Crews had to race to full combat positions immediately
- Off-duty personnel might be recalled depending on the scenario
2. Rapid Site Activation Nike sites were split into two main areas:
- Integrated Fire Control (IFC) – radar, tracking, and targeting
- Launcher Area (LA) – missiles, elevators, and launch rails During the ORE:
- Radars were powered up and calibrated
- Tracking systems locked onto simulated targets
- Launch crews prepared missiles (often using drill procedures rather than actual fueling/arming for safety)
3. Simulated Enemy Attack Evaluators introduced a mock air attack scenario, often escalating in complexity:
- Incoming “enemy” aircraft (simulated via radar inputs or scripts)
- Multiple targets requiring prioritization
- Electronic countermeasures or communication disruptions Crews had to:
- Detect and track targets
- Identify friend vs. foe
- Assign missiles and prepare to fire
4. Engagement Sequence (Simulated Launch) This was the core of the evaluation.
- Fire Control Officers issued engagement orders
- Launch crews executed the full firing sequence
- Missiles were not actually launched, but all steps up to launch were performed
5. Communications & Command Stress Test OREs heavily tested command structure:
- Orders flowed from higher headquarters down to the site
- Crews had to maintain clear, precise radio/phone communication
- Evaluators sometimes introduced confusion:
- Conflicting orders
- Simulated equipment failures
- Loss of communication lines
6. Casualty / Failure Scenarios To make things more realistic, evaluators often injected problems:
- “Radar failure” or degraded tracking
- Simulated wounded personnel
- Equipment malfunctions Crews had to adapt:
- Switch to backup systems
- Reassign roles
- Continue the mission without hesitation
7. Evaluation & Grading Observers—often from ARADCOM or higher command—were present throughout. They graded:
- Reaction time
- Procedural accuracy
- Crew coordination
8. Debrief (“Critique”) After the drill:
- Crews assembled for a detailed after-action review
- Every mistake and delay was dissected
- Evaluators provided blunt feedback
What Made OREs Tough
- No warning: you were judged on real readiness, not rehearsed performance
- High realism: scenarios mirrored expected Soviet bomber attacks
- Constant pressure: evaluators watched everything
- Team dependency: one weak link could hurt the entire site’s rating
